Feat(duckdb)!: support transpilation of SHA256 from bigquery to duckdb #6421
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When parsing SHA256 from BigQuery, we want to represent it as SHA2Digest with length 256 since the output is binary, just like we do with SHA1.
We also want to wrap SHA256 with UNHEX in the transpiled DuckDB query so that the output is binary to stay consistent with BigQuery.
For other dialects, we just want to make sure SHA2Digest with length 256 generates the appropriate queries. For example, SHA256(x) in bigquery should be tranpiled into SHA2_BINARY(x, 256) in Snowflake